Skip to content

fix: sequence number order #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 23, 2019
Merged

Conversation

seebees
Copy link
Contributor

@seebees seebees commented Jul 21, 2019

The sequence number must be honored.
This is especially important for non-signed algorithm suites.

The test vector added to this PR illustrates this.
It is the encrypted string ’asdf’ with a frame length of 1.
The frames have been rearranged to ’fdsa’.
Without this change the ESDK would decrypt this blob.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

The sequence number **must** be honored.
This is especially important for non-signed algorithm suites.

The test vector added to this PR illustrates this.
It is the encrypted string `’asdf’` with a frame length of 1.
The frames have been rearranged to `’fdsa’`.
Without this change the ESDK would decrypt this blob.
@seebees seebees requested a review from a team July 21, 2019 20:51
karlw00t
karlw00t previously approved these changes Jul 22, 2019
seebees added 2 commits July 22, 2019 09:15
Pass the error through the node stream better.
add test for browsers.
@seebees seebees merged commit b7dc81e into aws:master Jul 23, 2019
@seebees seebees deleted the sequence-number-order branch July 23, 2019 03:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants